Chromecast network #1080
Chromecast network #1080
Conversation
|
Please provide a description. |
docs/general/networking/index.md
Outdated
| @@ -15,7 +15,8 @@ HTTP and HTTPS are the primary means of connecting to the server. If using a sel | |||
|
|
|||
| :::caution | |||
|
|
|||
| In order for Chromecast to work on a non-public routable connection, 8.8.8.8 must be blocked on the Chromecast's Gateway. Blocking 8.8.8.8 on your router is the easiest solution to this problem. | |||
| In order for Chromecast to work on your local LAN, the easiest solution is to use IPv6 instead of IPv4. For a public routable IPv6 (not a link-local or ULA) there is no differentiation between public or local. An IPv6 address can simultaneously be publicly routable and accessible from the local LAN. | |||
There was a problem hiding this comment.
Will it work if I have a link local ipv6? (One that starts with fe80)
There was a problem hiding this comment.
I have not tested this but I think no. Chromecast needs a valid none self signed cert last time I checked. Since you can't create a fe80 (ULA) AAAA record with a valid lets encrypt cert, the IPv6 has to be public routable.
That is why I included the hint in the brackets.
Even if Chromecast supports self signed certs, this would be more complicated than just getting a let's encrypt cert, because you would still need a DNS override or NAT reflection and blocking the hardcoded google DNS. Then it has all the same problems IPv4 has.
There was a problem hiding this comment.
I made some changes to hopefully make it easier to understand for newcomers.
Explain the advantages of IPv6 in a beginner friendly way
Cloudflare Pages deployment
|
Add easier IPv6 option for Chromecast